System for onboarding participants of health services programs

ABSTRACT

A registration card or similar document (such as a boarding pass) may be used to onboard participants of health services programs. A data structure may store a plurality of unique identification codes linked to data elements providing personally identifiable information of participants. A document may then be generated to include an indicium, such as a QR code and/or bar code, for indicating the unique identification code for the participant, a personal identifier and a logistics detail for a biometric event. Upon receiving the unique identification code from the document, such as at the biometric event, the data element in the data structure may then be linked to an electronic medical record of the participant.

CROSS-REFERENCE(S) TO RELATED APPLICATION(S)

This application is a continuation in part of U.S. patent applicationSer. No. 14/608,988, filed on Jan. 29, 2015, entitled “System forElectronically Administering Health Services,” the entire contents ofwhich are hereby incorporated by reference into the present application.

BACKGROUND OF THE INVENTION

The present invention is directed to the field of health care, and moreparticularly, to a system and method for onboarding participants ofhealth services programs.

Health services programs typically involve providing a variety of healthrelated resources and content to individuals (users). Health servicesprograms may address a variety of health concerns, such as weight loss,nutrition counseling, diabetes control, smoking cessation, painmanagement, stress reduction, depression counseling, addictiontreatment, physical therapy, and the like. Resources for such programsmay include providers (such as doctors, nurses, counselors, coaches)conducting live sessions with individuals, whether in person, bytelephone, or otherwise, and individually or in groups; and deliveringrelevant content to individuals. Content may include: (1) informationalarticles (such as newsletters, reports, bulletins, recipes, exercises,e-mails, and blogs); (2) multimedia files (such as educational videos,pre-recorded webinars and audio tracks); and (3) interactive tools (suchas health calculators, calendars, journals and trackers, such as fortracking weight, mood, exercise, and the like).

Health services programs may be tailored to individuals according totheir age, health, gender and eligibility for benefits. With the recentimplementation of the U.S. Affordable Care Act (ACA) of 2010, providinghealth services programs which ensure continuing/follow-on care forindividuals is of heightened importance.

Today, providers may connect with individuals electronically (via theInternet), by telephone or in person. Providers may also deliverrelevant content to individuals, such as via e-mail or websites.However, providers must typically operate within the limited frameworkof a host platform which provides such capabilities in a disassociatedmanner. For example, a provider may use a networked personal computer(PC) to access an electronic communication mechanism. The provider maythen access a separate server to push content to the individual. Also,the provider may then access yet another server to record notes, updatescheduling information and/or perform other administrative tasks.However, switching between these environments oftentimes leads toinefficiency and potentially risks update errors.

In addition, individuals may undergo multiple “change-in-life” eventsover time. Change-in-life events can include, for example, changingone's name, marital status, listing of dependents, employment,insurance, health status, and so forth. As a result, providing a healthservices program to the same individual over time, including trackingthe individual's progress, is challenging. Adding to this difficulty,health information itself also typically requires security and safehandling to ensure patient privacy. For example, the U.S. HealthInsurance Portability and Accountability Act of 1996 (HIPAA) establishescertain guidelines for the secure treatment of Protected HealthInformation (PHI).

What is needed is an improved mechanism for more efficiently performingthe necessary tasks for administering a health services program. Also, amechanism for providing health services program to individuals, despitechange-in-life events, is needed. Also, there is a need for an improvedsystem for onboarding participants of health services programs.

This background information is provided to reveal information believedby the applicant to be of possible relevance to the present technology.No admission is necessarily intended, nor should be construed, that anyof the preceding information constitutes prior art against the presenttechnology.

SUMMARY OF THE INVENTION

The present inventors have determined that health services programs maybe efficiently administered by providing a plurality of health servicesmodules that are “horizontally integrated” on a platform. A rules engineis operative to identify enumerated events such that an event in onemodule triggers the rules engine to propagate a related event in one ormore other modules. Such health services modules may be componentsoperable for one or more of (1) live video conferencing, (2) scheduling,and/or (3) health services program data/content. Additional healthservices modules (“add-on modules”) may also be provided on the platformand similarly horizontally integrated, such as for (1) daily check-in,(2) managing medications, (3) updating/monitoring health number, (4)social access, and/or (5) rewards.

As used herein, “horizontally integrated”/“horizontal integration”refers to connections between modules at a common hierarchy level suchthat an update in one module propagates a related update in anothermodule. Integration of the aforementioned modules results in an enabledplatform that is readily portable to host platforms and optimized fordelivering health services programs with increased efficiency.Horizontal integration is accomplished using a rules engine connected toeach module that is configured to monitor enumerated events in themodules and propagate a change in other module corresponding to theenumerated event. Integrations include the ability to link variousmodules into a curriculum of care and coaching, for a cohesive programthat incorporates various modules for the optimization of outcomesthrough the education and influence of patients and plan members.

Module updates may be propagated as follows: (1) selecting diseasemanagement or health content via health services program data mayinitiate scheduling with providers for counseling sessions or classes,and may initiate countdowns, reminders and/or a “start now” link forvideo conferencing; (2) selecting scheduling data may initiate deliveryof particular health content, and may initiate countdowns, remindersand/or a “start now” link for video conferencing; and (3) selectingvideo conferencing may initiate delivery of particular health content(such as a provider pushing an article), may provide optional recordingof video conferencing data (such as a recorded mp3 or an automatedtranscript), may capture the call date/time, duration, completion,attendees or the like in scheduling data, and/or may trigger a follow upappointment in scheduling data. The modules may be integrated using APIinterfaces and may tie in to a host platform providing health contentand scheduling information via embedded service calls.

In addition, “unique identification codes” may be associated with (1)classes of health services programs or “health cubes,” and (2) healthinformation about particular individuals possessing the uniqueidentification codes. Moreover, unique identification codes may belinked to health services programs and related content for individualsgroups of health programs, qualification criteria and pricing specifiedby specific clients. By determining common relationships between healthinformation associated with differing identification codes, theidentification codes can be linked to persistently provide healthbenefits for the same individual over time, despite changes in codes.Also, by associating a measurement result specific to an individual witha unique identification code, specific programs based the measurementresult can be recommended, and participation by individuals can beencouraged. Participation and use of modules creates track-able andreportable activities that can be leveraged in analytics and reporting,for purposes such as incentives management and progress reporting.

The system may be deployed in scalable environments, such as via cloudcomputing, to provide cost-effective program offerings. Accordingly, byintegrating embodiments of the present invention, host platforms maydeliver health programs while focusing on the quality of the healthbenefit offerings. Integration can be achieved via portable modulesmaking Application Program Interface (API) calls or via white labelpages that may be embedded.

The system may also utilize Java Script Object Notation (JSON),Representational State Transfer (REST) and/or other standards,architectural styles or techniques to provide integration capabilitywith host platforms. In addition, information can be advantageouslyextracted via pre-prepared reports, such as via Extensible MarkupLanguage (XML), Extensible Stylesheet Language Transformations (XSLT)and/or XML Schema Definition (XSD) files.

The system may also provide Data as a Service (DaaS) by storing healthinformation about individuals and/or related aspects. Configurable dataanalytics and quantitative and qualitative analysis results may also bedetermined and made available, such as via secure reports and/or APIcalls.

It is also contemplated to provide a curriculum-building program foreasily creating and defining health services activities or other assets,grouping such assets into an event, including with notifications,incentives, and so forth, and arranging such events along a programtimeline. The combination of content and delivery as prescribed in anadministrator designed engagement curriculum is a unique approach forscripting partial and total experiences for individuals and groups ofindividual users.

Specifically, one aspect of the invention may provide a horizontallyintegrated system for administering a health services program executableon an electronic computer according to a program stored in anon-transient medium to implement: a plurality of modules, including:(a) a video conferencing module configured to enable live videoconferencing over a computer network: and (b) a health services moduleconfigured to index a plurality of health services content; and a rulesengine in communication with each of the plurality of modules. The rulesengine may be configured to provide an update to at least one of theplurality of modules according to an event that occurs in another of theplurality of modules.

The plurality of modules could also include a scheduling moduleconfigured to receive scheduling information relating to a plurality oftime slots for health services. The plurality of modules could alsoinclude one or more “add-on” modules.

Another aspect may provide a method for administering a health servicesprogram from an electronic computer providing a video conferencingmodule configured to enable live video conferencing sessions over acomputer network, a health services module configured to index aplurality of health services content, and a scheduling module configuredto receive scheduling information relating to a plurality of time slotsfor health services. The method may include: (a) monitoring an eventthat occurs in a first module, the first module being at least one ofthe video conferencing module, the health services module and thescheduling module; and (b) providing an update in a second moduleaccording to the event, the second module being at least one of thevideo conferencing module, the health services module and the schedulingmodule.

Another aspect may provide a system for building a curriculum forproviding health services, the system executable on an electroniccomputer according to a program stored in a non-transient medium to: (a)provide a first health services program that includes a first set ofhealth services activities; (b) provide a second health services programthat includes a second set of health services activities, the secondhealth services program different from the first health servicesprogram; and (b) graphically display the first and second sets of healthservices activities with respect to a common timeline.

In addition, the present inventors have determined that a registrationcard or similar document (such as a boarding pass) may be used toeffectively onboard participants of health services programs. A datastructure may store a plurality of unique identification codes linked todata elements providing personally identifiable information ofparticipants. A document may then be generated to include an indicium,such as a QR code and/or bar code, for indicating the uniqueidentification code for the participant, a personal identifier and alogistics detail for a biometric event. Upon receiving the uniqueidentification code from the document, such as at the biometric event,the data element in the data structure may then be linked to anelectronic medical record of the participant.

As a result, a biometric screening event may be streamlined by giving aparticipant a single document which may be used, among other things, totie into the participant's medical record, provide an instructionindicating a type of biometric measurement to be taken, capture results,and the like, while identifying the participant quickly by simplyverifying a government-issued identification.

Accordingly, another aspect may provide an improved system foronboarding a participant of a health services program. The system mayinclude: a data structure containing a plurality of uniqueidentification codes, each of the unique identification codes beinglinked to a data element providing personally identifiable informationof a participant; and a document for providing to a participant. Thedocument may include: (a) an indicium indicating a unique identificationcode from among the plurality of unique identification codes in the datastructure; (b) a personal identifier of the participant, the personalidentifier being included in a data element providing personallyidentifiable information of the participant, the data element beinglinked to the unique identification code in the data structure; and (c)a logistics detail for a biometric event. Upon receiving the uniqueidentification code from the document, the data element providingpersonally identifiable information of the participant may be furtherlinked to an electronic medical record of the participant.

Another aspect may also provide an improved method for onboarding aparticipant of a health services program. The method may include:storing a plurality of unique identification codes in a data structure,each of the unique identification codes being linked to a data elementproviding personally identifiable information of a participant;providing a document to a participant, the document including: (a) anindicium indicating a unique identification code from among theplurality of unique identification codes in the data structure; (b) apersonal identifier of the participant, the personal identifier beingincluded in a data element providing personally identifiable informationof the participant, the data element being linked to the uniqueidentification code in the data structure; and (c) a logistics detailfor a biometric event; and upon receiving the unique identification codefrom the document, linking the data element providing personallyidentifiable information of the participant to an electronic medicalrecord of the participant.

These and other features and advantages of the invention will becomeapparent to those skilled in the art from the following detaileddescription and the accompanying drawings. It should be understood,however, that the detailed description and specific examples, whileindicating preferred embodiments of the present invention, are given byway of illustration and not of limitation. Many changes andmodifications may be made within the scope of the present inventionwithout departing from the spirit thereof, and the invention includesall such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred exemplary embodiments of the invention are illustrated in theaccompanying drawings in which like reference numerals represent likeparts throughout, and in which:

FIG. 1 is a block diagram illustrating a horizontally integrated systemfor administering a health services program in communication with a hostplatform in accordance with an embodiment of the invention;

FIG. 2 is a diagram illustrating a first data structure linking uniqueidentification codes to health cubes in accordance with an embodiment ofthe invention;

FIG. 3 is a diagram illustrating an exemplar mechanism for providingunique identification codes to individuals in accordance with anembodiment of the invention;

FIG. 4 is a diagram illustrating a second data structure for linkingunique identification codes to health information of individuals inaccordance with an embodiment of the invention;

FIG. 5 is a diagram illustrating a plurality of health servicesactivities, including content and time slots, arranged with respect to atimeline via a graphical display in accordance with an embodiment of theinvention;

FIG. 6 is a block diagram illustrating operation of the horizontallyintegrated system of FIG. 1 in a system environment;

FIG. 7 is a diagram illustrating a graphical view for delivery of thehealth services program of FIG. 1 to an individual;

FIG. 8 is a diagram illustrating expanded tiles of the graphical view ofFIG. 7;

FIG. 9 is a flow diagram illustrating an exemplar system for onboardingparticipants of health services programs; and

FIG. 10 is an exemplar document for providing to participants withrespect to FIG. 9.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT System Architecture

Referring now to FIG. 1, a computing environment 10 includes ahorizontally integrated system 12 for administering a health servicesprogram in accordance with an embodiment of the invention. Thehorizontally integrated system 12 may be implemented, for example, via acloud computing server, a private cloud or intranet server, or privatedesktop, and may be in communication with a host system 14. Thehorizontally integrated system 12 includes a plurality of modules,including a video conferencing module 16, a health services module 18and a scheduling module 20. The video conferencing module 16, the healthservices module 18 and the scheduling module 20 may be softwarearchitectural components operable for computing functions including livevideo conferencing, indexing health services program data/content andscheduling, respectively. A rules engine 22 is in communication witheach of the plurality of modules.

The video conferencing module 16 is configured to enable live videoconferencing over a computer network such as the Internet. The videoconferencing module 16 may implement an Internet telephony architecturewhich may be based on a peer-to-peer connection scheme. The videoconferencing module 16 may open multiple ports via communications port24 to enable communications with multiple clients, which may correspondto individuals (users) and providers (doctors, nurses, counselors,coaches, and the like), among multiple simultaneous sessions.Accordingly, video conferencing sessions may be one-to-one (such as aprivate counseling session between an individual and a provider) orone-to-many (such as a group session led by a provider with multipleattendees in which many attendees can see and talk to the providerand/or each other during sessions).

The health services module 18 is configured to index a plurality ofhealth services content. As such, the health services module 18 maycommunicate with the host system 14, via the rules engine 22, toretrieve raw health services programs and content data which may bestored in a host platform content database 26. Health services programsmay include a variety of content pre-arranged by the host for addressingvarious health concerns such as weight loss, nutrition counseling,diabetes control, smoking cessation, pain management, stress reduction,depression counseling, addiction treatment, physical therapy, and thelike. Content may include: (1) informational articles (such asnewsletters, reports, bulletins, recipes, exercises, e-mails, blogs, andthe like); (2) multimedia files (such as educational videos,pre-recorded webinars or audio tracks, and the like); (3) interactivetools (such as health calculators, calendars or journals), and the like.

As described below with respect to FIG. 2, the health services module 18may use a first data structure 30 (which could be separately stored) tolink “unique identification codes” to “health cubes” including healthservices programs and related content for individuals. In addition, asdescribed below with respect to FIG. 4, the health services module 18may use a second data structure 32 (which could be separately stored) tolink the unique identification codes to health information aboutindividuals possessing the unique identification codes. Upon receiving aunique identification code from an individual, the health servicesmodule 18 may determine programs and content eligible to the individualbased on the health cube and health information linked to the uniqueidentification code. Accordingly, the rules engine 22 may operate tolimit the health services module 18 to delivering content according tothe unique identification code which may be set by eligibility status.

The scheduling module 20 is configured to receive scheduling informationrelating to a plurality of time slots for health services. Accordingly,the scheduling module 20 may communicate with the host system 14, viathe rules engine 22, to retrieve raw scheduling and calendaring datawhich may be stored in a host platform scheduling database 28. This mayinclude time slots on given dates by particular providers for particulartopics. For example, one health coach may have a 30 minute time slotavailable four times a week for smoking cessation, while another healthcoach may have a 45 minute time slot two times a week for diabetescontrol.

The scheduling module 20 may use a local data structure 34 (which may beseparately stored) for indexing scheduling data for providers andmaintaining a virtual calendaring and appointment system. Accordingly,the scheduling module 20 may allow an individual to view time slotavailabilities (by times and dates) for the various providers and/orvarious subjects of interest. For example, an individual may find, viathe scheduling module 20, a time slot for a particular pain managementcoach or a next available pain management coach, and may request anappointment accordingly. Requesting the appointment may temporarily holdthe time slot reserved while the scheduling module 20 executes toconfirm eligibility, confirm availability, request/secure payment,finalize the appointment and/or send notifications.

The rules engine 22, in communication with each of the plurality ofmodules, is configured to provide an update to the video conferencingmodule 16, the health services module 18 and/or the scheduling module 20according to monitored events that occurs in other modules. In otherwords, the rules engine 22 may identify an enumerated event in a firstmodule, such that the event triggers the rules engine to propagate arelated event in a second, thereby providing horizontal integrationbetween the first and second modules.

By way of example, a video conferencing session via the videoconferencing module 16 may be an event which triggers the rules engine22 to update the scheduling module 20, such as to record a completion ofthe video conferencing session on the particular date/time with aparticular duration, or which triggers the rules engine 22 to update thehealth services module 18 to deliver content to an individual that isrelated to the video conferencing session (such as a nutrition articlerelated to a diabetes control session). Similarly, a selection of a timeslot via the scheduling module 20 may be an event which triggers therules engine 22 to update the health services module 18 to deliver orotherwise make available content related to the selection back to theindividual, or which triggers the rules engine 22 to update the videoconferencing module 16 to initiate a timer according to the selection ofthe time slot, which could serve as a continuous reminder or countdownthe session, followed by a button to automatically launch the session.Likewise, a selection of content via the health services module 18 maybe an event which triggers the rules engine 22 to update the videoconferencing module 16 to suggest a video conferencing session to join(such as a selecting a tobacco article leading to suggestion to join asmoking cessation session), or may be an event which triggers the rulesengine 22 to update the scheduling module 20 to suggest a time slot,such as for a particular provider or health subject, related to theselection (such as a selecting a tobacco article leading to a suggestionto schedule a time with a smoking cessation counselor).

Accordingly, the rules engine 22 enables connections between theaforementioned modules at a common hierarchy level such that an updatein one module propagates a related update in another module. Integrationof the aforementioned modules results in an optimized platform that isreadily portable to host platforms, including those with user/providerports and raw content, such as the host system 14.

Additional health services modules (“add-on modules”) may also beprovided on the horizontally integrated system 12 within the spirit ofthe invention. For example, an add-on module 36 may be simultaneously orsubsequently deployed to the horizontally integrated system 12 toprovide additional functionality. The rules engine 22 may havepredefined hooks for monitoring events and propagating updates forvarious possible add-on modules, and/or the rules engine 22 may beupdated, such as in software or firmware, to utilize new hooks formonitoring events and propagating updates. Examples of the add-on module36 include: (1) a daily check-in module; (2) a managing medicationsmodule; (3) an updating/monitoring health number module; (4) a socialaccess module; and/or (5) a rewards module. Additional aspects of theaforementioned modules are described with respect to FIGS. 7 and 8.

The rules engine 22 and the aforementioned modules may each include anApplication Program Interface (API) element 38 for enabling crosscommunication and/or exposing integrated functionality. The API element38 may also facilitate portability of the horizontally integrated system12 for connection with the host system 14.

The rules engine 22 may also be in communication with an analytic engine40. The analytic engine 40 may provide interactive functionalitydirected toward reporting and analytics for managers and executives. Theanalytic engine 40 may include an API element 38 for communicating withother modules, and may communicate with an analytic data structure 42for mass information storage, and/or for exposing integratedfunctionality. Accordingly, the analytic engine 40 may provide Data as aService (DaaS) and may allow, among other things, out of the box reportsfor executives and managers; data analytics with point and click accessto various cross sectional information; and support for informationstorage or data warehousing for extended periods, such as greater thanseven years.

In the environment 10, the horizontally integrated system 12, via therules engine 22, may also be in communication with a real time clock(RTC) 44 or another precision time protocol element. The RTC 44 mayprovide close synchronization between the aforementioned modules.

In embodiments, the rules engine 22 may also allow, among other things,providing industry standard authentication protocol information forsharing across enterprise platforms, such as in accordance with openstandard for authorization (OAuth) 1.0; authenticating and updatingprofiles and branding information of health systems, providers,insurers, agents, brokers or employers; authenticating and updatingprofile information of counselors; configuring privileges given toorganizations, members and counselors to obtain access to other modules;providing internal accounting, accounts payable and receivables forbilling and invoicing; implementing extracts, transfers and loads (ELF)of information to and from external systems such as incentivesmanagement, claims management, pharmacies and electronic medical record(EMR) systems; providing dynamic content publishing, such as ofarticles, recipes and videos; and providing alerts and notificationssent via e-mail and/or Short Message Service (SMS) text messaging duringvarious stages of workflow.

The horizontally integrated system 12 may be deployed in scalableenvironments, such as cloud computing a private cloud or intranet, or aprivate desktop, to provide cost-effective program offerings. Thehorizontally integrated system 12 could be provided via “Software as aService” (SaaS), and embodiments may also utilize JSON, REST and/orother standards, architectural styles or techniques to provideintegration capability with host system 14 as known in the art. Inaddition, information in the modular architecture can be advantageouslyextracted via pre-prepared reports, such as via XML, XSLT and/or XSDfiles.

In operation, the host system 14 may deliver content to the horizontallyintegrated system 12, such as from the host platform content database 26and the host platform scheduling database 28. An individual or user maythen access the host system 14 via a user interface 50. Similarly, aprovider may access the host system 14 via a provider interface 52, andan administrative agent may access the host system 14 via an admininterface 54. Differing access points allow differing access rights andprivileges in the environment 10, with the admin interface 54essentially allowing maintenance ability. Moreover, each access pointmay be customized with respect to its own sets of rights and privileges.For example, various levels of the provider interface 52 may grantaccess to specific pieces of an individual's information based onpermissions granted to the provider by the client or entity.Accordingly, a health coach, for example, might see all of anindividual's information, including personal health information, via theprovider interface 52, while a case manager might only see contact andstatus information via the same provider interface 52.

The host system 14 may provide front end interfaces to users andproviders, such as external web site access via the user interface 50,and internal web site access via the provider interface 52. The hostsystem 14 then receives requests from the user interface 50 and/or theprovider interface 52, and forwards the requests to the horizontallyintegrated system 12 for processing. The horizontally integrated system12, in turn, processes the requests and returns processed data to thehost system 14 for serving to the user interface 50 and/or the providerinterface 52.

Data Flow

Referring now to FIG. 2, a diagram illustrating the first data structure30 linking unique identification codes 62 to health cubes 64 whichinclude health services programs and related content for individuals isprovided in accordance with an embodiment of the invention. The uniqueidentification codes 62 may include any number of data patterns ofvarying configurations and length. For example, in an embodiment, alphanumeric patterns, such as “33-AQR-54665” or “MZ-4XMZ-U9F,” may be used.

The health cubes 64 may represent classes of structured health servicesprograms 66, each including a plurality of pre-approved, relevantcontent 68. Health services programs 66 may represent structuredcurriculums for a variety of health subjects, such as weight loss,nutrition counseling, diabetes control, smoking cessation, painmanagement, stress reduction, depression counseling, addictiontreatment, physical therapy, and the like. Pre-approved, relevantcontent 68 for each program may include: (1) informational articles(such as newsletters, reports, bulletins, recipes, exercises, e-mails,blogs, and the like); (2) multimedia files (such as educational videos,pre-recorded webinars or audio tracks, and the like); (3) interactivetools (such as health calculators, calendars or journals); and (4)scheduling for live sessions.

The health cubes 64 are divided according to categories, tiers orgroups, such as groups “A,” “B” and “C,” which provide health servicesprograms and content for individuals with identification codesassociated with the group. Associations may be configured, for example,based on health insurance benefits that individuals are eligible toreceive. In addition, or alternatively, content 68 of the health cubes64 may be unstructured or free from particular health services programs66. By way of example, as illustrated in FIG. 2, “Code 1,” “Code 2” and“Code 3” may be linked to health cube “A” for a first set of healthservices programs and content, while “Code 4” and “Code 5” may be linkedto health cube “B” for a second set of health services programs andcontent. Accordingly, Codes 1, 2 and 3 may be provided to threeindividuals associated with a first employer, while Codes 4 and 5 may beprovided to two individuals associated with second employer.

Referring now to FIG. 3, a diagram illustrating an exemplar mechanismfor providing unique identification codes to individuals is provided inaccordance with an embodiment of the invention. An individual 70 mayparticipate in an event which produces a measurement result 72 specificto the individual 70. For example, the individual 70 may be part ofgroup in which many individuals have their blood pressure,height/weight, eyesight or other health related characteristicsmeasured.

Next, a unique identification code 62 is provided to the particularindividual 70, such as a registration card 76 prompting the individual70 to take action to register the unique identification code 62. Theregistration card 76 may include, for example, a uniform resourcelocator (URL) or web address prompting the individual 70 to go online,such as to the host system 14 via the user interface 50, to submit theunique identification code 62 for registration. In addition, oralternatively, the registration card 76 may include a quick response(QR) code 78, a bar code 80 and/or any other indicia for the individual70 to scan, such as via a smart phone or tablet, for faster action toregister the unique identification code 62. The individual 70 may beencouraged to do so, for example, to receive the measurement result 72,reports or analyses relating to the measurement result 72 and/or programdata or content associated with the measurement result 72. Theregistration card 76 may also include health information 82 about theindividual 70, such as the individual's name or employer, as well asinformation about the provider.

The unique identification code 62 and/or the registration card 76 may bemailed, e-mailed, personally delivered, or otherwise distributed to theindividual 70. In addition, unique identification code 62 and/or theregistration card 76 could also be provided without participation in anevent and/or without the measurement result 72. However, participationin an event and/or producing the measurement result 72 may be effectivetools for encouraging participation by the individual 70.

Alternatively, eligibility lists may be provided which can be checked,for example, during a registration process. As such, codes assigned to aclient may then, in turn, be assigned to individual payers.

Referring now to FIG. 4, a diagram illustrating the second datastructure 32 linking unique identification codes 62 to healthinformation of individuals possessing the unique identification codes isprovided in accordance with an embodiment of the invention. Healthinformation about individuals, such as that collected during the eventdescribed with respect to FIG. 3, is then linked to the uniqueidentification code 62. For example, health information 94 correspondingto health data about the individual 70 may be linked to “Code 1.” Inaddition, data spaces 96 may be reserved for linking health informationabout other individuals to other unique identification codes. The healthinformation 94 may comprise a first data element 98 corresponding to themeasurement result 72 and a second data element 100 corresponding topersonally identifiable information and/or protected health informationabout the individual, such as the health information 82. Accordingly,programs and content eligibility may be determined for an individual,and limited accordingly, based on the health cube and health informationlinked to the unique identification code.

If an individual has been in different programs, such as via the same ordifferent clients or entities providing codes, the individual can belinked via common health information associated with the codes. Forexample, if multiple codes are determined to be associated with commonpersonally identifiable information, those codes may be linked such thatcurrent and future information about an individual is accuratelymaintained.

A curriculum building process provides for easily creating and defininghealth services activities or other assets, grouping such assets intoone or more events, including with notifications, incentives, and soforth, and arranging such one or more events along a program timeline.Accordingly, the combination of content and delivery as prescribed in anadministrator designed engagement curriculum is a unique approach forscripting partial and total experiences for individuals and groups ofindividual users.

Referring now to FIG. 5, a diagram 101 illustrates a plurality of healthservices activities 102, including content and time slots, arranged withrespect to a common timeline 104 via a graphical display in accordancewith an embodiment of the invention. When an individual selects aprogram 66, content 68 with respect to the program may be graphicallydisplayed to the individual over the timeline 104 via the rules engine22. This may be particularly useful for work load balancing,particularly when multiple programs are enrolled.

For example, a user may select enrollment in a first program “A” whichmay correspond to diabetes control. As a result, a first set of healthservices activities denoted “A1” through “A9” may appear as ticks, marksor other notations that are individually mapped with respect to thetimeline 104 which may represent weeks. In week 1, health servicesactivity A1 may correspond to a live video conferencing session with adiabetes counselor; in week 2, health services activity A2 maycorrespond to another live video conferencing session with a diabetescounselor, and health services activity A3 may correspond to content forreview, such as an informational article; and so forth. The user mayalso select enrollment in a second program “B,” which may correspond tosmoking cessation. As a result, a second set of health servicesactivities denoted “B1” through “B11” may also appear as ticks, marks orother notations that are individually mapped with respect to thetimeline 104. Also, the second set of health services activities B1through B11 may be displayed with the first set of health servicesactivities A1 through A9 on the timeline 104 to illustrate loadbalancing.

The health services activities 102 may be color coded to correspond toan activity type. For example, health services activities 102corresponding to live video conferencing sessions may be orange, healthservices activities 102 corresponding to content may be red, and soforth. Moreover, the health services activities 102 may each behyperlinks or other points of access for further information about therespective activity, such as via the modules of the horizontallyintegrated system 12.

In addition, a client or entity may define a permissible set of livesession types and allow a member to request a session that is notdefined as part of a program. For example, a member could be in aprogram with a defined set of events, and also be allowed to request anadditional event, such as a live session with a counselor, that is notdefined as part of the program. The additional event could be provided,for example, for a fee or complimentarily.

Also, the curriculum design allows for the rules engine 22 to update therules engine update health services activities according to events thatoccur in one or more of the modules. For example, notifications, alertsand/or incentives may be automatically applied to curriculum componentssuch as health services activities 102. A data structure, such as areference table, may be maintained for tracking such updates, includingnotifications, alerts and/or incentives, and communicating with othermodules of the horizontally integrated system 12.

System Environment

Referring now to FIG. 6, a block diagram illustrating operation of thehorizontally integrated system 12 in a system environment is provided inaccordance with an embodiment of the invention. The individual 70 mayuse a computer 112, smart phone, tablet or other computing device toaccess, via a computer network 114 (which may be the Internet), the hostsystem 14. In an SaaS configuration, the host system 14 may then, inturn, access a cloud computing environment 118 (or alternatively, aprivate cloud or intranet or desktop). The cloud computing environment118 may include a server 116 which includes a network interface 120, aprocessor 122 and a non-transient memory 124 for executing thehorizontally integrated system 12 as described above with respect toFIG. 1. The server 116 may also be in communication with a mass storage130 for holding the first data structure 30, the second data structure32, and the like.

The host system 14 may provide a host company's website, for example,and communicate with the horizontally integrated system 12 via API's orembedded service calls. In an alternative arrangement, the horizontallyintegrated system 12 may be directly integrated in the host system 14,or may be distributed over multiple computer systems. A separate managersystem 134 may also be provided for admin access and maintenanceability.

In operation, the individual 70 may navigate to the host system 14 andsubmit a unique registration code via the user interface 50. The hostsystem 14 may, in turn, forward the unique registration code to theserver 116. The server 116 may, in turn, execute, for example, thehealth services module 18 to register the individual 70. The server 116may then execute to display a measurement result specific to theindividual 70 to the computer 112, and may determine and display aprogram data and content relevant to the measurement result and theindividual 70. For example, if the measurement result relates to avision test, the server 116 could execute to provide a visual acuityresult to the individual 70 and an analysis of the result as compared toage or peers, in addition to a vision insurance benefit for eyeglasses,a newsletter concerning maintaining good eye health, an advertisementfor discounts on eyeglasses, and so forth.

The individual 70 may proceed to obtain allowable content via the healthservices module 18. The individual 70 may also proceed to schedule timeslots via the scheduling module 20. The individual 70 may also proceedto engage in live video conferencing session via the video conferencingmodule 16. The individual 70 may also view health services activities102 with respect to a time line for work load balancing via the computer112.

User Experience

Referring now to FIG. 7, a diagram illustrating a first graphical view150 for delivery of the health services program of FIG. 1 to anindividual thereby providing a user experience is provided in accordancewith an embodiment of the invention. Upon authentication of a uniqueidentification code or proper login credentials, the individual 70 maybe presented with the first graphical view 150 via the computer 112. Thefirst graphical view 150 may include a welcome screen with a header 152followed by a banner 154. The header 152 may include links for obtaininghelp, obtaining mail messages, accessing account settings, logging outand/or similar functions. The banner 154 may include links indicatingthe time and date, upcoming events and reminders, pending tasks for theindividual, health tips for the individual, and/or a quick pulsequestion for the individual (relating, for example, to mood, opinion orknowledge). An area below graphically displays a plurality of tiledlinks 156 generally relating to the implemented modules of thehorizontally integrated system 12. The links may appear, for example, asa plurality of tiled icons.

For example, a first tiled link 160, which may be titled “Live Session,”may relate to the video conferencing module 16. An active timer 162 maybe actively displayed over the first tiled link 160 to serve as acountdown (and continuous reminder) for the next live video conferencingsession. Clicking on the active timer 162 during the countdown may be anevent in the video conferencing module 16 which triggers the rulesengine 22 to display scheduling information for the next live videoconferencing session to the graphical display via the scheduling module20. When it is time to join a next video conferencing session, the timer162 may transition to a “Join Now” link to initiate the videoconferencing session when clicked. Accordingly, the rules engine 22 maymonitor events from and provide updates to video conferencing module 16as described above with respect to FIG. 1.

A second tiled link 164, which may be titled “Schedule,” may relate tothe scheduling module 20. Scheduling indicia 166 may be activelydisplayed over the second tiled link 164 to serve as a notification of apending scheduling activity for a time slot. Accordingly, the rulesengine 22 may monitor events from and provide updates to the schedulingmodule 20 as described above with respect to FIG. 1.

A third tiled link 168, which may be titled “Daily Check-In,” may relateto the daily check-in module, which may be an add-on module. The dailycheck-in module may provide, for example, information relating to goals,notes, journal activity, and so forth, and may link to other moduleswhich may provide related content. Accordingly, the rules engine 22 maymonitor events from and provide updates to the daily check-in module.

A fourth tiled link 170, which may be titled “Program Resources,” mayrelate to the health services module 18. Accessing the health servicesmodule 18 may allow access to programs and content which may includelinks, for example to scheduling and video conferencing sessions.Accordingly, the rules engine 22 may monitor events from and provideupdates to the health services module 18 as described above with respectto FIG. 1.

A fifth tiled link 172, which may be titled “Medications,” may relate tothe managing medications module, which may be an add-on module. Themedications module may allow inputting and tracking medications. Certainmedications could trigger the rules engine 22, for example, to propose avideo conferencing session, a time slot or content related to themedication, or provide a reward, via the rewards module, forconsistently taking the medication. Accordingly, the rules engine 22 maymonitor events from and provide updates to the social access module.

A sixth tiled link 174, which may be titled “Health Numbers,” may relateto the updating/monitoring health number module, which may be an add-onmodule. The updating/monitoring health number module may allow enteringhealth numbers, such as cholesterol levels, triglyceride levels, bloodpressure, weight, and so forth, for tracking and monitoring over time.Certain health numbers could trigger the rules engine 22, for example,to propose a video conferencing session, a time slot or content, such asa stress reduction program and content for consistently high bloodpressure levels. Accordingly, the rules engine 22 may monitor eventsfrom and provide updates to the updating/monitoring health numbermodule.

A seventh tiled link 176, which may be titled “Social,” may relate tothe social access module, which may be an add-on module. The socialaccess module may allow sharing updates or links with others, forexample, as a link to content from the health services module 18.Accordingly, the rules engine 22 may monitor events from and provideupdates to the social access module.

An eight tiled link 178, which may be titled “Rewards,” may relate tothe rewards module, which may be an add-on module. The rewards modulemay track incentives, such as cash rewards and discounts, for variousevents, such as attending video conferencing sessions, viewing content,and so forth. Accordingly, the rules engine 22 may monitor events fromand provide updates to the rewards module.

Referring now to FIG. 8, a diagram illustrating expanded tiles of asecond graphical view 200 is provided. The individual 70 could swipeacross screens between the first and second graphical views 150 and 200,respectively, selecting one or more of the aforementioned tiled links todynamically display more information associated with the tiled links.For example, the first tiled link 160 (“Live Session”) may include thetimer 162, now timing a duration of an active video conferencingsession, and a communications window 202 for the video conferencing. Thesecond tiled link 164 (“Schedule”) may include a calendar 204 and anappointments/reminders area 206 for highlighting upcoming appointmentsand reminder times. The third tiled link 168 (“Daily Check-In”) mayinclude a goals/notes area 208 for tracking goals and recording notesand an activity tracker 210. The fourth tiled link 170 (“ProgramResources”) may include a links area 212 to a plurality of programs andcontent, as well as a multimedia area 214 for viewing content. The fifthtiled link 172 (“Medications”) may include a medications listing area216, with icons for adding or subtracting medications, and a timelinearea 218 for tracking dates/times for taking medications. The sixthtiled link 174 (“Health Numbers”) may include a data entry area 220 forinputting health numbers, along with links, for example, for updatingthe information and/or retrieving historical information. The seventhtiled link 176 (“Social”) may include a social update area 222 forpreparing statements, content, links or otherwise for sharing, as wellas social links 224 for selecting social media outlets. The eight tiledlink 178 (“Rewards”) may include a rewards area 226 for tracking rewardsand incentives.

A link from various sources, such as from the events/reminders in thebanner 154, the daily check-in module, the health numbers module, or thelike, may lead to displaying the measurement result 72 described abovewith respect to FIG. 3. For example, a pop-up window 230, specific tothe individual 70, may be displayed upon selecting one of theaforementioned links, along with related program data and content 232which may correspond to the measurement result 72.

Onboarding Participants

Referring now to FIG. 9, a flow diagram illustrating an exemplar system300 for onboarding participants of health services programs is provided.A participant 302 may initially provide personally identifiableinformation in a registration step 304. The personally identifiableinformation may comprise any information that is specific to theparticipant 302 for the purpose of uniquely identifying the participant302 from other participants. The personally identifiable information mayinclude, for example, one or more of the following: the participant'sname, age, date of birth, home and/or work address, phone number, emailaddress, social security number, insurance information, an electronicmedical record, and the like. The personally identifiable informationmay be received by an employee, provider, system operator, or otherwise,and may correspondingly be entered as a data element 306 in a datastructure 308 (which data structure 308 may be part of a first databasestored in a non-transient medium and executing on a server).

In addition, the data structure 308 may operably store a plurality ofunique identification codes 310 (or unique registration codes),illustrated by way of example as “Code 1,” “Code 2,” “Code 3,” and soforth. The unique identification codes may comprise alpha numeric(and/or symbolic) patterns or sequences, such “33-AQR-54665,”“MZ-4XMZ-U9F,” or “RCH 113442 042214 A E,” so long as the codes aresufficiently unique from one another.

Upon receiving and entering the data element 306 providing thepersonally identifiable information in the data structure 308, the dataelement 306 may be linked to a particular unique identification code 310(such as Code 1). In this manner, as personally identifiable informationof additional participants are further entered into the data structure308, additional corresponding data elements 306 may similarly be linkedto additional unique identification codes 310. As a result, eachparticipant entered in the data structure 308 may be associated with aparticular unique identification code 310.

Next, the participant 302 may be linked in the data structure 308 to oneor more biometric events, each having logistics information 312. Abiometric event (or health screening event) may be any health relatedactivity that may be provided for the participant 302. A biometric eventmay be organized by an employer, a provider, or the like, and maypreferably include obtaining a biometric measurement of the participant302. Biometric measurements may include, for example, measuring aparticipant's heart rate, blood pressure, cholesterol level, glucoselevel, height, weight, visual acuity, auditory acuity, physical fitness,dexterity, and the like. A participant may be linked to a biometricevent based, for example, on a selection of benefits available from anemployer, including such as a corresponding health cube 64 as describedabove with respect to FIG. 2. The logistics information 312 may include,for example, a date, time and/or location (such as an address and/orprovider name) for the biometric event, illustrated as “Event 1” by wayof example. The logistics information 312 may be provided by an employeror other entity, and may be entered in the data structure 308 tocorrespond with select participants 302 for biometric eventsaccordingly.

In addition, the data element 306 may be further linked to aninstruction 314 for a provider at the biometric event. For example, theinstruction 314, which may be accessed later by the provider at thebiometric event for indicating useful information to the provider, suchas no blood testing, in need of visual or auditory acuity testing and/orother similar pieces of information.

Next, in a generation step 316, a document 318, which may be aregistration card or “boarding pass,” may be generated by the system 300and provided to the participant 302. The document 318 may include anindicium 320 for indicating the particular unique identification code310 (from among the plurality of unique identification codes 310 in thedata structure 308) linked to the participant 302. The indicium maycomprise, for example, a QR code and/or bar code that may be scanned toreveal the unique identification code 310, and/or the uniqueidentification code 310 in alphanumeric form. In one aspect, additionalsecurity may be provided by including on the document 318 informationassociated with an image for the patient. For example, upon reading theindicium 320, an image of the patient, such as from the patient'semployee file, could be displayed on a provider's screen in order tofurther confirm the patient's identity.

The document 318 may also include a personal identifier 322 of theparticipant 302. The personal identifier 322 may be an aspect of thedata element 306 (providing the personally identifiable information ofthe participant 302) linked to the particular unique identification code310 in the data structure 308. For example, the personal identifier 322may be the name of the participant 302.

The document 318 may also include a logistics detail 324 and/or otherinstruction information for the biometric event. The logistics detail324 may be an aspect of the logistics information 312, such as the date,time and/or a location for the biometric event. In one aspect, theindicium 320 could be further applied to provide the logistics detailand/or other instruction information.

Next, in providing step 330, the document 318 is provided to theparticipant 302. The document 318 may be provided to the participant 302as a virtual document that may be displayed on a screen of an electronicdevice, such as a tablet or smartphone. In addition, or alternatively,the document 318 may be provided as a physical document (such as inpaper form) operable for handling by the participant 302.

Next, in onboarding step 332, the participant 302 may attend thebiometric event (Event 1) at the appointed time and location inaccordance with the logistics detail 324 provided on the document 318.At the biometric event, a provider or system operator may then read theindicium 320 to determine the unique identification code 310, and inturn the data element 306, of the participant 302. In addition, theprovider or system operator may optionally verify the participant'sidentity using a secondary source, such as a government-issuedidentification shown by the participant 302. The provider or systemoperator may also observe the instruction 314 linked to the data element306.

Next, in measurement step 340, a biometric measurement result 342 may beobtained from the participant 302 by the provider or system operator.The biometric measurement result 342 may be a measure, for example, ofthe participant's heart rate, blood pressure, cholesterol level, glucoselevel, height, weight, visual acuity, auditory acuity, physical fitness,dexterity, or the like. The biometric measurement result 342 may then belinked to the data element 306 (providing personally identifiableinformation of the participant 302) in the data structure 308.

Having successfully on-boarded the participant 302 from the registrationstep 304 through measurement step 340, in a connection step 344, theprovider or system operator may then link the data element 306(providing personally identifiable information of the participant 302)to an electronic medical record 350 of the participant 302 (whichelectronic medical record 350 may be part of a second database 352stored in a non-transient medium and executing on a server, and/or apart of the data element 306 in the data structure 308). The electronicmedical record 350 of the participant 302 may be one of plurality ofelectronic medical records for various individuals, some of which may beparticipants. The electronic medical record 350 may be a collection ofelectronic health information about an individual in digital format thatmay be capable of being shared across different health care settings.

Referring now to FIG. 10, an exemplar document 318 for providing toparticipants as described above with respect to FIG. 9 is provided. Thedocument 318 may have the appearance and feel of a traditional airlineboarding pass. The document 318 may be a paper document or a virtualdocument displayed on a screen 360 of an electronic device, such as atablet, smartphone or other computer.

Accordingly, the participant 302 could select a first link 362 to printthe document 318, which may produce a physical document (in paper form)that may be handled by the participant 302. The participant 302 couldalso select a second link 364 to push the document 318 to a smartphoneor mobile computing device if it is not already being viewed in suchform. The participant 302 could also select a third link 366 to closethe window to cease displaying the document 318.

In one aspect of the invention, the document 318 may optionally comprisetwo portions which may be physically or virtually detachable from oneanother. A first portion 370 may comprise a larger portion of thedocument 318 which may be taken by the operator or system provider atthe biometric event and kept on file. A second portion 372 may comprisea smaller portion of the document 318 which may be retained by theparticipant 302 for the participant's proof of participation and/orrecords. Both the first portion 370 and the second portion 372 of thedocument 318 may include the indicium for indicating the particularunique identification code 310, the personal identifier and thelogistics detail for the biometric event as described above with respectto FIG. 9.

For example, the first portion 370 may include a bar code 380 forindicating the unique identification code 310, in addition to the uniqueidentification code 310 in alphanumeric form 382. The first portion 370may also include the participant's name 384 as a personal identifier.The first portion 370 may also include a date, time and location 386 forthe biometric event as the logistics detail.

Similarly, the second portion 372 may include a QR code 390 forindicating the unique identification code 310, in addition to the uniqueidentification code 310 in alphanumeric form 392. The second portion 372may also include the participant's name 394 as a personal identifier.The second portion 372 may also include a location 396 for the biometricevent as the logistics detail.

Alternative embodiments may implement various features described abovein hardware and/or software and with varying levels of integration. Inaddition, alternative embodiments may combine or further separate ordistribute hardware elements, or software elements, as may beappropriate for the task.

Although the best mode contemplated by the inventors of carrying out thepresent invention is disclosed above, practice of the above invention isnot limited thereto. It will be manifest that various additions,modifications and rearrangements of the features of the presentinvention may be made without deviating from the spirit and the scope ofthe underlying inventive concept.

What is claimed is:
 1. An electronic system for linking a biometricmeasurement to an electronic medical record (EMR) of a participant, thesystem comprising a computer executing a program stored in anon-transient medium to: store in a first data structure a plurality ofunique identification codes, each of the unique identification codesbeing linked to a data element providing personally identifiableinformation of a participant; generate a document for providing to aparticipant, the document including: (a) an indicium indicating a uniqueidentification code from among the plurality of unique identificationcodes in the data structure; (b) a personal identifier of theparticipant, the personal identifier being from the data elementproviding personally identifiable information of the participant, thedata element being linked to the unique identification code in the datastructure; and (c) a logistics detail for a biometric event forobtaining a biometric measurement of the participant; after generationof the document, electronically link a biometric measurement result ofthe participant associated with the biometric event indicated by thedocument to the data element providing personally identifiableinformation of the participant, and electronically link the data elementproviding personally identifiable information of the participant, linkedto the biometric measurement, to an EMR of the participant stored in asecond data structure, the EMR comprising a collection of electronichealth information about the participant in a digital format.
 2. Thesystem of claim 1, wherein the biometric measurement result comprisesany of a heart rate, a blood pressure, a cholesterol level and a glucoselevel.
 3. The system of claim 1, wherein the logistics detail comprisesany of a date and a location for the biometric event.
 4. The system ofclaim 1, wherein the first and second data structures comprise first andsecond databases, respectively.
 5. The system of claim 1, wherein thedocument is a virtual document operable for display on a screen of anelectronic device.
 6. The system of claim 1, wherein the document is aphysical document operable for handling by the participant.
 7. Thesystem of claim 1, wherein the indicium is at least one of a QR code anda bar code for indicating the unique identification code, and whereinthe unique identification code is an alpha numeric sequence.
 8. Thesystem of claim 1, further comprising the data element providingpersonally identifiable information of the participant being furtherelectronically linked to an instruction indicating a type of biometricmeasurement.
 9. The system of claim 1, wherein the personallyidentifiable information comprises any of a name, an age, an address anda phone number, and the personal identifier is the name.
 10. A methodfor linking a biometric measurement to an EMR of a participant, themethod comprising: storing in a first data structure plurality of uniqueidentification codes, each of the unique identification codes beinglinked to a data element providing personally identifiable informationof a participant; generating a document for a participant, the documentincluding: (a) an indicium indicating a unique identification code fromamong the plurality of unique identification codes in the datastructure; (b) a personal identifier of the participant, the personalidentifier being from the data element providing personally identifiableinformation of the participant, the data element being linked to theunique identification code in the data structure; and (c) a logisticsdetail for a biometric event for obtaining a biometric measurement ofthe participant; after generating the document, electronically linking abiometric measurement result of the participant associated with thebiometric event indicated by the document to the data element providingpersonally identifiable information of the participant, andelectronically linking the data element providing personallyidentifiable information of the participant, linked to the biometricmeasurement, to an EMR of the participant stored in a second datastructure, the EMR comprising a collection of electronic healthinformation about the participant in a digital format.
 11. The method ofclaim 10, wherein the biometric measurement result comprises any of aheart rate, a blood pressure, a cholesterol level and a glucose level.12. The method of claim 10, wherein the logistics detail comprises anyof a date and a location for the biometric event.
 13. The method ofclaim 10, wherein the first and second data structures a comprise firstand second databases, respectively.
 14. The method of claim 10, whereinthe document is a virtual document, and further comprising displayingthe virtual document on a screen of an electronic device.
 15. The methodof claim 10, wherein the document is a physical document operable forhandling by the participant.
 16. The method of claim 10, wherein theindicium is at least one of a QR code and a bar code for indicating theunique identification code, and wherein the unique identification codeis an alpha numeric sequence.
 17. The method of claim 10, furthercomprising electronically linking the data element providing personallyidentifiable information of the participant to an instruction indicatinga type of biometric measurement.
 18. The method of claim 10, wherein thepersonally identifiable information comprises any of a name, an age, anaddress and a phone number, and the personal identifier is the name.